Skip to content

add support for CONDA_PREFIX set already in vscode environment#1243

Merged
eleanorjboyd merged 1 commit intomicrosoft:mainfrom
eleanorjboyd:crude-lark
Feb 18, 2026
Merged

add support for CONDA_PREFIX set already in vscode environment#1243
eleanorjboyd merged 1 commit intomicrosoft:mainfrom
eleanorjboyd:crude-lark

Conversation

@eleanorjboyd
Copy link
Member

@eleanorjboyd eleanorjboyd self-assigned this Feb 18, 2026
@eleanorjboyd eleanorjboyd added the bug Issue identified by VS Code Team member as probable bug label Feb 18, 2026
@vs-code-engineering vs-code-engineering bot added this to the February 2026 milestone Feb 18, 2026
@eleanorjboyd eleanorjboyd merged commit b546ac4 into microsoft:main Feb 18, 2026
34 checks passed
@davidfokkema
Copy link

Is there an easy way for me to test this on my setup or should I better wait until this is released?

@eleanorjboyd
Copy link
Member Author

The fix for this issue has been shipped in the latest pre-release (nightly) build of the Python Environments extension which you can now test!

How to install the pre-release version:

Open VS Code
Go to the Extensions view (Cmd+Shift+X on macOS / Ctrl+Shift+X on Windows/Linux)
Search for "Python Environments"
Click on the extension to open its details page
Click the "Switch to Pre-Release Version" button (next to the Uninstall button)
Reload VS Code if prompted
How to verify you're on the pre-release:

The extension version should show a pre-release identifier (e.g., 2026.x.xxxxx with a timestamp)
On the extension page, you'll see "Pre-Release" badge and the option to "Switch to Release Version"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Issue identified by VS Code Team member as probable bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Starting VS Code from conda environment fails to activate that environment

3 participants

Comments